New Features in The JavaBeans Bridge for ActiveX Beta 5

1. The Bridge does not rely on any environment variable (CLASSPATH or PATH).
2. The PropertyPages concept of the ActiveX world are now supported. Any JavaBeans component that define a Customizer will have a property page.
3. PropertyChange and VetoableChange are now forwarded like normal OLE events so Visual Basic Script can be attached to these events.

Bugs Corrected since Beta-4

1. Customizer would be displayed as a property page in the wrong location in Visual C++ 5.0.
2. QueryInterface in IConnectionPoint was not implemented correctly.
3. Parameters of methods would not be evaluated correctly in Visual Basic 5.0 when there is only one argument.
4. OLEIVERB_HIDE would crash Lotus Approach 97.
5. Registry window would appear during JavaBeans packaging time.
6. Bridge would not load with JRE
7. Bad registry data formats for InPlace objects
8. Various metafile painting

Bugs Corrected since Beta 3

1. Event stub generation would fail when one of the event property would be of type Object[].
2. Events would not be forwarded in some ActiveX containers like Excel 97.

Bugs Corrected since Beta 2

1. Property change notification was incorrectly forwarded for stock properties.
2. Direct connection between components was generating an exception.
3. Look in the documentation for an example how to hook up components directly while running through the bridge.
4. Invisible beans were not supported.

Bugs Corrected since Beta 1

1. The Packager would fail if the Bean is not a part of a package. The packager would raise an exception when trying to package a Bean which is not part of a package.
2. Persistence problems. The JavaBeans Bridge for ActiveX would fail when trying to load/save multiple times in some containers like Word 95.
3. Word Crashes when using frame display. The JavaBeans Bridge for ActiveX would fail after displaying a JavaBeans component in Word 95 as a frame picture.
4. The Bridge would not load when the licensing key was requested. The Bridge was not implementing a licensing key by itself. You need to modify the hooks provided to allow correct licensing. The bridge was not dealing correctly with Containers that check the license key.
5. Various IDispatch problems (Parameter passing and packaging).
6. Design Mode problems. The bridge was not handling correctly some Design mode ambient properties.

    

Miscellaneous

Please note that there are repaint glitches in Visual Basic while running certain Beans in Design Mode. Use Visual Basic "Run Mode" to get an actual view of your JavaBeans.

Use the Bug Report page (on the Javasoft web page) to report bugs in the JavaBeans bridge for ActiveX.